See how libass project compares to other vendors in security performance
libass 0.15.x before 0.15.1 has a heap-based buffer overflow in decodechars (called from decodefont and processtext) because the wrong integer data type is used for subtraction.
Last updated 26 August 2025
In libass 0.14.0, the assoutlineconstruct's call to outlinestroke causes a signed integer overflow.
The checkallocations function in libass/assshaper.c in libass before 0.13.4 allows remote attackers to cause a denial of service (memory allocation failure) via unspecified vectors.
Buffer overflow in the calccoeff function in libass/assblur.c in libass before 0.13.4 allows remote attackers to cause a denial of service via unspecified vectors.
Libass released a new 0.13.4 version which fixes multiple issues. CVE-2016-7971 remains unfixed for now.
CVE-2016-7969 upstream patch:
https://github.com/libass/libass/pull/240/commits/b72b283b936a600c730e00875d7d067bded3fc26
CVE-2016-7970 upstream patch:
https://github.com/libass/libass/pull/240/commits/08e754612019ed84d1db0d1fc4f5798248decd75
CVE-2016-7972 upstream patch:
https://github.com/libass/libass/pull/240/commits/aa54e0b59200a994d50a346b5d7ac818ebcf2d4b
External References:
https://github.com/libass/libass/releases/tag/0.13.4